fix: Resolve panic with ElementKeyInt(0): can't use tftypes
#2800
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
Description
This commit updates the
manifest/morph/scaffold.gologic in order toresolve a panic encountered when working with
Tupletypes.Also adds a new unit test to cover this case.
Disclaimer: This fix and the coresponding test case was generated by
Gemini, and has been reviewed and tested by myself.
Acceptance tests
Output from acceptance testing:
Release Note
Release note for CHANGELOG:
References
Fixes: #2778 #2754 plus probably others...
Community Note